NTISthis.com

Evidence Guide: ICTSAS413 - Manage resolution of system faults on a live system

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAS413 - Manage resolution of system faults on a live system

What evidence can you provide to prove your understanding of each of the following citeria?

Determine maintenance methodologies and repositories

  1. Identify the nature of modification to the system
  2. Confirm existence and currency of repositories
  3. Review repositories for changes and develop new backup procedures
  4. Prepare or check modification request forms and levels of authority for sign-off
  5. Develop a hierarchy of modifications and the response for each
  6. Determine backup and blackout strategies in place
Identify the nature of modification to the system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm existence and currency of repositories

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review repositories for changes and develop new backup procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare or check modification request forms and levels of authority for sign-off

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop a hierarchy of modifications and the response for each

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine backup and blackout strategies in place

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Implement change management system

  1. Follow standards and procedures for logging the change request
  2. Document expected impact to user base during implementation
  3. Identify levels of possible failure and related reporting procedures
  4. Document expected outcomes of the modification
  5. Inform user of modification implications
  6. Assign modification to appropriate person for actioning
Follow standards and procedures for logging the change request

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document expected impact to user base during implementation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify levels of possible failure and related reporting procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document expected outcomes of the modification

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Inform user of modification implications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assign modification to appropriate person for actioning

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Report review of results

  1. Complete aspects of the change system and ensure modification is tested and operational
  2. Prepare report and deliver to appropriate person, indicating the results of modification
  3. Update and amend documentation and repositories
Complete aspects of the change system and ensure modification is tested and operational

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare report and deliver to appropriate person, indicating the results of modification

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update and amend documentation and repositories

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine maintenance methodologies and repositories

1.1 Identify the nature of modification to the system

1.2 Confirm existence and currency of repositories

1.3 Review repositories for changes and develop new backup procedures

1.4 Prepare or check modification request forms and levels of authority for sign-off

1.5 Develop a hierarchy of modifications and the response for each

1.6 Determine backup and blackout strategies in place

2. Implement change management system

2.1 Follow standards and procedures for logging the change request

2.2 Document expected impact to user base during implementation

2.3 Identify levels of possible failure and related reporting procedures

2.4 Document expected outcomes of the modification

2.5 Inform user of modification implications

2.6 Assign modification to appropriate person for actioning

3. Report review of results

3.1 Complete aspects of the change system and ensure modification is tested and operational

3.2 Prepare report and deliver to appropriate person, indicating the results of modification

3.3 Update and amend documentation and repositories

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine maintenance methodologies and repositories

1.1 Identify the nature of modification to the system

1.2 Confirm existence and currency of repositories

1.3 Review repositories for changes and develop new backup procedures

1.4 Prepare or check modification request forms and levels of authority for sign-off

1.5 Develop a hierarchy of modifications and the response for each

1.6 Determine backup and blackout strategies in place

2. Implement change management system

2.1 Follow standards and procedures for logging the change request

2.2 Document expected impact to user base during implementation

2.3 Identify levels of possible failure and related reporting procedures

2.4 Document expected outcomes of the modification

2.5 Inform user of modification implications

2.6 Assign modification to appropriate person for actioning

3. Report review of results

3.1 Complete aspects of the change system and ensure modification is tested and operational

3.2 Prepare report and deliver to appropriate person, indicating the results of modification

3.3 Update and amend documentation and repositories

Evidence of the ability to:

identify the required modifications

itemise the expected outcomes of the modifications

implement the modifications

document and report on the modifications.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

describe the key features of change control procedures

describe the key features of the client business domain including the role of stakeholders and the degree of stakeholder involvement

describe the key features and capabilities of current industry accepted hardware and software products

analyse the key features of help desk and maintenance practices

discuss quality assurance practices

explain the process for system testing

outline the system's current functionality and describe the features and functions of the system under modification

identify and summarise industry standards that apply to the information and communications technology (ICT) industry.